I'm trying to compile a 'ye old VB6 COM Object in a Nant Task in CruiseControl.NET and for some reason I get this error:

ThoughtWorks.CruiseControl.Core.Tasks.BuilderException: NAnt process timed out (after 600 seconds) at ThoughtWorks.CruiseControl.Core.Tasks.NAntTask.Run(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.Project.Run(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.RunBuild(IIntegrationResult result) at ThoughtWorks.CruiseControl.Core.IntegrationRunner.RunIntegration(BuildCondition buildCondition) BaseDirectory: , Targets: , Executable: C:\Program Files\CI\nant-0.85-rc3\bin\nant.exe, BuildFile: default.build]

I've tried adding:

    <tasks>
      <nant>
        <executable>C:\Program Files\CI\nant-0.85-rc3\bin\nant.exe</executable>
        <buildArgs>-D:solution.name=SiteManagerV28 -D:vss.db=\\awimgimp01\vss.net\ -D:vss.password= -D:vss.username=jthake</buildArgs>
        <nologo>false</nologo>
        <buildFile>default.build</buildFile>
        <buildTimeoutSeconds>3200</buildTimeoutSeconds>
      </nant>
    </tasks>

...to try and set it higher and it doesn't like it at all. It permantly returns 600 seconds as the error. The running time for the CruiseControl.NET Project is always about 00:12:22 when I force it.

I've got other VB6 projects compiling and registering as a COM object fine at the same time and although the source code is complex it doesn't take that long to compile of the command line standalone.

Don't you just hate those little red error messages on your Continuous Integration? And I've just installed the CCTray too which now gives me MSN Messenger type pop ups of status of builds too! I can see that being uninstalled or ignored quite quickly!